Skip to content

feat: make workflow computable without instantiating dependents #1647

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 9, 2022

Conversation

metacosm
Copy link
Collaborator

@metacosm metacosm commented Dec 3, 2022

Depends on #1648

@metacosm metacosm self-assigned this Dec 3, 2022
@metacosm metacosm requested a review from csviri December 3, 2022 19:09
@metacosm metacosm force-pushed the further-workflow branch 2 times, most recently from 91d8d44 to fac0211 Compare December 3, 2022 22:23
@metacosm
Copy link
Collaborator Author

metacosm commented Dec 5, 2022

Replaces #1641.

@csviri
Copy link
Collaborator

csviri commented Dec 5, 2022

Do we still need the DependentResourceConfigurator interface?

@metacosm
Copy link
Collaborator Author

metacosm commented Dec 6, 2022

Do we still need the DependentResourceConfigurator interface?

Unless you have a way to remove it, yes, we still need it as it's still used in the code.

@csviri
Copy link
Collaborator

csviri commented Dec 6, 2022

Just added 2 remarks, 1 is just conceptuial idea, otherwise makes sense, I like the changes :)

@metacosm metacosm added this to the 4.2 milestone Dec 9, 2022
Copy link
Collaborator

@csviri csviri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@metacosm metacosm changed the base branch from main to next December 9, 2022 12:56
This allows for workflows to be computed at build time, only to be
resolved (i.e. associating workflow nodes to actual dependent
resources) when needed.
In the process, the configuration mechanism of managed dependent
resource has been improved to make it possible to resolve the
configuration solely from the dependent resource class instead of
previously requiring the dependent to be instantiated. This is now done
viw the DependentResourceConfigurationResolver class.
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 27 Code Smells

57.8% 57.8% Coverage
0.0% 0.0% Duplication

@metacosm metacosm merged commit f159a29 into next Dec 9, 2022
@metacosm metacosm deleted the further-workflow branch December 9, 2022 14:00
metacosm added a commit to quarkiverse/quarkus-operator-sdk that referenced this pull request Dec 9, 2022
metacosm added a commit to quarkiverse/quarkus-operator-sdk that referenced this pull request Dec 11, 2022
metacosm added a commit that referenced this pull request Dec 14, 2022
…es (#1647)

This allows for workflows to be computed at build time, only to be
resolved (i.e. associating workflow nodes to actual dependent
resources) when needed.
In the process, the configuration mechanism of managed dependent
resource has been improved to make it possible to resolve the
configuration solely from the dependent resource class instead of
previously requiring the dependent to be instantiated. This is now done
viw the DependentResourceConfigurationResolver class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants